📊 Packages dist files size difference

Thanks for the PR! Here is the difference in size of the packages dist files between the base branch and the PR.
Please review the changes and make sure they are expected.

hi there, this is one of a kind.. i had a look recently about svelte 5/asset mapper and i ran into the same, so following what i thought i wrote a rollup.config.js (inspired from this repo) on top of this branch to put all the things together
after a while and some distorsions ^^ i managed to render something but it's a big mess at least
anyway i feel this is not the right way things should be done with assetmapper as i got to use a module bundler
there is already a step to compile .svelte files and it's quite unpleasant tho
i could give extra details if it sounds interesting

Hey @maxperei, sure, any help would be appreciated! :)

ok well, i generated a patch to give a try
of course you'll have to npm i && npm run build again (as well as php bin/console assetmap:install if necessary)
then if you go into ./assets/vendor/svelte you see a new file : index-client.js and a bunch of other files like svelte.index.js, internal/client.js which are overridden and the left ones remain unchanged
this particular index-client.js is very tricky because sometimes it throws a 404 and you will have to expose this file into public/ folder using php bin/console asset-map:compile or just copy it, and sometimes (maybe it's symfony cache or something i can't explain --') it works without exposing it

Hey @maxperei and sorry for the late reply, support for Svelte 5 is something I've put on the side for a while, but I'd really like to finish this task.

I tried your solution, which is indeed super hacky, but it's still one solution among... 0 other solutions 😅

I've just rebased and force-pushed this PR, and moved the ux.symfony.com things to symfony/ux.symfony.com#32, the files svelte/internal/client.js and svelte/svelte.index.js looks better, but it contains an unresolved dependency to custom-element.js (even if the file exists... maybe the AssetMapper import resolver is missing it?)

I will try to open an issue on Svelte to see if they can provide a JSDeliver/ESM-compatible build, that will be easier for everyone.

Hey @Kocal

I came across this post on X which reminded me of the issue we had when trying to integrate Svelte 5 in the initial PR:
https://x.com/joyofcodedev/status/2038259907451928807

I tried applying the same importmap approach with esm.sh cdn, and it seems to work in a minimal setup with a pre-built component:
https://codesandbox.io/p/devbox/svelte-importmap-forked-q8858g?workspaceId=ws_CJ7KxeYW5eGLozWC7m7Lw5

This might be a good starting point for a solution!

Hi, and thanks for the suggestions!

Unfortunately, after several months of failed attempts, I think we’re simply going to drop support for Svelte 5 with AssetMapper in UX Svelte 3.

Their CDN build is completely broken, and I’d rather have nothing (or at least, just support with Webpack Encore) than have to go to great lengths to try and get it working with AssetMapper.

If anyone in the future decides to add Svelte 5 support for AssetMapper by offering a clean solution, it will be a pleasure!